Re: Getting started contributing.

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Feb 4, 2013, 13:37 UTC
Message-ID: <vpq4nhsmc7p.fsf@grenoble-inp.fr>
In-Reply-To: <7vhaltalre.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 12 quoted lines

> adamfraser <adamfraser0@gmail.com> writes:
>
>> I would like to start contributing to git and am looking for a small project
>> idea to get started with. On the  Small Project Ideas wiki
>> <https://git.wiki.kernel.org/index.php/SmallProjectsIdeas>   site there is a
>> suggestion for adding a 'git rebase --status' command that sounds like it
>> would be good for someone who has little knowledge of the code base.
>
> I think the two patches Duy just posted tonight overlap with that
> topic, and I suspect it would give the end users a better experience
> to put the information in "git status" output rather than a separate
> "git rebase" subcommand.

(I'm the one who wrote the idea on the wiki)

"git status" already shows a lot of valuable information about rebase, but my idea was that there's still room for a much more verbose command (hence too verbose to appear in the output of "git branch" or "git status"), saying eg.

* Which patch is being applied (we can imagine giving just the subject
  line by default, but showing the complete patch with an additional
  --patch option). I often miss that when trying to understand the
  origin of a conflict. I can manually look at file
  .git/rebase-merge/patch (I seem to remember a patch that shows the
  path to this file when rebase stops, but I can't find it anymore), but
  a nice porcelain would be nice.

* What's still on the todo-list

Also, perhaps this could gather the advices "(run git rebase <something> to <do something>)" currently in the output of "git status", and "git status may just say "(run git rebase --status for more information)" instead of 2 or 3 lines of advices.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/