Opened 11 years ago

Closed 11 years ago

#10782 closed enhancement (fixed)

update docs with info on mercurial rebase extension

Reported by: kini Owned by:
Priority: major Milestone: sage-4.6.2
Component: documentation Keywords:
Cc: Merged in: sage-4.6.2.rc1
Authors: Keshav Kini Reviewers: Dmitrii Pasechnik
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by kini)

As named. See this sage-devel post for more info.

Attachments (1)

trac_10782-docs-about-sage-upgrade-with-rebase.patch (1.8 KB) - added by kini 11 years ago.

Download all attachments as: .zip

Change History (15)

comment:1 Changed 11 years ago by kini

  • Authors set to Keshav Kini
  • Status changed from new to needs_review

comment:2 Changed 11 years ago by kini

  • Owner changed from kini to (none)

comment:3 Changed 11 years ago by mvngu

  • Milestone set to sage-4.7

comment:4 Changed 11 years ago by dimpase

  • Status changed from needs_review to positive_review

merges OK, reads meaningful.

comment:5 Changed 11 years ago by kini

  • Description modified (diff)

Apply to sagenb

comment:6 Changed 11 years ago by kini

  • Description modified (diff)

Oops, wrong ticket!

(Thanks, Dima, for the positive review!)

comment:7 Changed 11 years ago by rbeezer

Hi Kini,

Thanks for this - looks like Dima beat me to a review.

Have you seen hg qpush --move some_patch.patch in the newest versions of Mercurial? Let's you grab an unapplied patch out of any position in the unapplied stack to push on.

Rob

comment:8 follow-up: Changed 11 years ago by kini

Hi Rob,

Sure. Yes, I've heard of it, and even use it :) But I didn't see how to work it in here what with the topic of this post. How many "different" things are supposed to fit into a single ticket, anyway? I saw your post on sage-devel about upgrading the developer guide, and it seems like it would be easier to just edit the docs and be done with it rather than submitting dozens of patches. (Well, I suppose that's what the Sage Wiki is for...)

-Keshav

comment:9 in reply to: ↑ 8 Changed 11 years ago by rbeezer

Replying to kini:

Hi Keshav,

Just upgraded my OS, so now have a version of Mercurial with "--move" - been anxiously awaiting it. It will make the Developers Guide better, no need to talk about editing the series file. Just passing it along, in case you hadn't seen it. ;-)

No - wasn't suggesting that for this ticket, or a new incremental ticket. I'll try to round up a few details like this for the reorganization proposed in sage-devel. Post there if you have any more tips or tricks!

Thanks, Rob

comment:10 Changed 11 years ago by jdemeyer

  • Milestone changed from sage-4.7 to sage-4.6.2
  • Reviewers set to Dmitrii Pasechnik

comment:11 follow-up: Changed 11 years ago by jdemeyer

  • Status changed from positive_review to needs_work

Please add ticket number to the first line of the commit message.

comment:12 in reply to: ↑ 11 Changed 11 years ago by kini

  • Status changed from needs_work to needs_review

Replying to jdemeyer:

Please add ticket number to the first line of the commit message.

Done.

comment:13 Changed 11 years ago by dimpase

  • Status changed from needs_review to positive_review

comment:14 Changed 11 years ago by jdemeyer

  • Merged in set to sage-4.6.2.rc1
  • Resolution set to fixed
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.