Re: [PATCH v21 0/19] rs/ref-transaction (Re: Transaction patch series overview)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 18, 2014, 17:26 UTC
- Message-ID
- <xmqq4mw4q1qc.fsf@gitster.dls.corp.google.com>
- In-Reply-To
- <20140918165721.GA772@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 10 quoted lines
> Junio C Hamano wrote: > >> Jonathan: Is a current version of this patch series set up to be >> fetched so that it can be reviewed outside Gerrit? > > The current tip is 06d707cb63e34fc55a18ecc47e668f3c44acae57 from > https://code.googlesource.com/git (fetch-by-sha1 should work). Each > reroll gets its own refname of the form refs/changes/62/1062/<number> > with <number> increasing. The "Download" widget in the top-right > corner of https://code-review.googlesource.com/1062 shows the refname.
While I am showing my naiveté, how does one figure out that 1062 is the last one in the series?
Does the order of changes that appear in
https://code-review.googlesource.com/#/q/project:git+branch:master+topic:ref-transaction
have any significance? e.g. is a "topic" supposed to be a single strand of pearls on top of the "branch", and the top one is the tip, or something?
> There are plenty of unaddressed comments from Michael, so I'd hold off > on picking up the latest for pu for now.
Oh, the request was not for that. I simply cannot read the patch with only limited context in the web browser without having a ready access to a coherent whole, i.e. a full tree with history, to review a change like this.