Re: [PATCH v4] git-svn: clarify the referent of dcommit's optional argument

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 17, 2012 at 8:49 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Jon Seymour <jon.seymour@xxxxxxxxx> writes:
>
>>> +Originally, 'git svn' recommended that developers pulled or merged from
>>> +the 'git svn' branch.  This was because the author favored `git svn set-tree B`
>>> +to commit a single head rather than the `git svn set-tree A..B` notation to
>>> +commit multiple commits. Use of 'git pull' or 'git merge' with `git svn set-tree A...B`
>>
>> A...B -> A..B
>>
>> Will fix in next iteration, assuming Junio and Eric are otherwise
>> happy with the update.
>
> I don't have an opinion on the latter half of the patch that is primarily
> about the rationale given by "the author", i.e. Eric ;-), but the
> description of dcommit subcommand itself certainly looks simpler and more
> readble to me.
>
> Thanks.
>
>

Ok, I'll fix the ... issue mentioned above and (also some trailing
whitespace) once Eric has given his feedback or acknowledgement.

jon.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]