Thank you Junio, maybe I will have another chance to get practice
sending a v2 patch.
On Fri, Sep 21, 2018 at 09:32:00AM -0700, Junio C Hamano wrote:
> frede...@ofb.net writes:
>
> > On Thu, Sep 20, 2018 at 06:23:03PM +0200, Duy Nguyen wrote:
> >> On Wed, Sep 19, 2018 at 03:59:58PM -0700, Junio
> Patches are welcome.
I'd be happy to patch git-contacts to link to the message you just
sent, then maybe someone more qualified would know where to start... :)
Frederick
On Fri, Sep 21, 2018 at 01:18:30AM -0400, Eric Sunshine wrote:
> On Wed, Sep 19, 2018 at 6:49 PM Junio C Hamano wrote:
> >
On Thu, Sep 20, 2018 at 06:23:03PM +0200, Duy Nguyen wrote:
> On Wed, Sep 19, 2018 at 03:59:58PM -0700, Junio C Hamano wrote:
> > > @@ -23,7 +26,7 @@ OPTIONS
> > >
> > > --mode=::
> > > Specify layout mode. See configuration variable column.ui for option
> > > - syntax.
> > > + syntax (in
> I think "Is it a CPU archtecture?" is a red-herring, but between
It wasn't meant to be a red-herring though. Plenty of Linux
distributions have different architecture-specific package repos, and
arch is a common abbreviation for architecture. This only comes up if
you search for the full word
Hi Jonathan and Git developers,
I poked around today and figured out how to reorder the command
listings in the manual page, they are taken from git/command-list.txt
so I just reorder the lines in that file (after disabling sorting in
git/Documentation/cmd-list.perl).
I haven't reordered the
Hello Jonathan,
Thank you for replying to me earlier. I just wanted to follow up on
this thread. Did you decide not to go with my proposal?
Next week I should have time to send you a patch with the manual page
reordered... although, unless you have a special 'diff' which can
detect when text has
Hi Jonathan,
If it's really just a matter of needing someone with a newcomer's
perspective, then I'd be happy to look over the ordering of the git
subcommands. You can run the command I provided to glean the frequency
of each subcommand from your shell history, I'll look over the output
and see
Thank you Jonathan for signaling your willingness to adopt the
documentation philosophy I suggested. That's a quite valuable first
step. Unfortunately my contribution will have to be limited for the
moment to making this suggestion, as I am extraordinarily busy. I hope
it will not be too
Dear Git Developers,
I am trying to learn how to use Git but I've been put off by not
knowing where to start. I would like to start with the 'git' man page,
but it lists the Git subcommands in alphabetical order, rather than in
an order which would be useful for learners. For example, I'm not
9 matches
Mail list logo
