From: Matthias Andree <matthias.andree@gmx.de>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Could this be done simpler?
Date: Thu, 25 Jun 2009 18:32:51 +0200 [thread overview]
Message-ID: <4A43A6B3.5020407@gmx.de> (raw)
In-Reply-To: <863a9oz8lh.fsf@blue.stonehenge.com>
Randal L. Schwartz schrieb:
>>>>>> "Junio" == Junio C Hamano <gitster@pobox.com> writes:
>
> Junio> (5) Continue pretending to be Linus, complete the octopus. The key is to
> Junio> let the "fetch" phase of this to append to the FETCH_HEAD, not
> Junio> replacing it.
>
> Junio> $ git pull --append \
> Junio> git://git.kernel.org/pub/scm/linux/kernel/git/viro/audit-current \
> Junio> for-linus
>
> The relatively current doc of "--append" looks like this:
>
> -a, --append
> Append ref names and object names of fetched refs to the existing
> contents of will be overwritten.
>
> I read this three times, and still don't know what it means (and it doesn't
> even scan well as English), so I would have never known to use this strategy.
> Can you explain this more in detail, or point at something in the mailing list
> that does?
Greetings,
If I may: So the existing description is incomprehensible. I sort of believed I
understood it, but apparently I didn't understand enough of it.
Could we ditch the current git-pull --append description? Can then please
somebody rewrite this paragraph? This somebody must have completely understood
(1) what this feature is good for (practically speaking)
(2) how it works (technically speaking, to provide reference information)
That would be much more useful, and the use would last longer :-)
I don't dare ask Junio directly.
However, it appears to me that git-pull already does most of what Linus needs,
could take some final cosmetic touch-ups WRT logs. So could somebody please
rewrite this?
And if I may be so bold: Please rewrite before somebody starts polishing the
bisect facilities WRT octopus merges. These seem unrelated, as in: you don't
need to make bisect more convenient to be able to fix the description of
git-pull --append...
Thanks for not slashing me to pieces. 8-)
Best regards
MA
next prev parent reply other threads:[~2009-06-25 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 21:35 Could this be done simpler? Linus Torvalds
2009-06-25 1:04 ` Junio C Hamano
2009-06-25 14:33 ` Randal L. Schwartz
2009-06-25 16:32 ` Matthias Andree [this message]
2009-06-25 17:25 ` Junio C Hamano
2009-06-25 21:54 ` Matthias Andree
2009-06-27 0:26 ` Junio C Hamano
2009-06-25 18:32 ` Junio C Hamano
2009-06-25 17:19 ` Michael J Gruber
2009-06-25 22:02 ` Christian Couder
2009-06-25 22:23 ` Christian Couder
2009-06-25 22:29 ` Junio C Hamano
2009-06-25 22:50 ` Linus Torvalds
2009-06-25 23:17 ` Junio C Hamano
2009-06-25 22:55 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A43A6B3.5020407@gmx.de \
--to=matthias.andree@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=merlyn@stonehenge.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).