git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Felipe Contreras" <felipe.contreras@gmail.com>, <git@vger.kernel.org>
Subject: Re: My patches
Date: Sat, 12 Oct 2013 17:18:10 +0100	[thread overview]
Message-ID: <5247B8D59AAE41F3A0D8BF165D2C2BAE@PhilipOakley> (raw)
In-Reply-To: 20131012072450.GA21165@nysa

From: "Felipe Contreras" <felipe.contreras@gmail.com>
Sent: Saturday, October 12, 2013 8:24 AM
> Hi,
>
> Clearly, a lot of my patches have not been reviewed properly, so even
> though they are technically correct, and would benefit users, some 
> have
> specifically been requested by them, and at least one would
> significantly improve Git's user interface...

Hi Filipe,

Given you have put a lot of work into your 16 patch series, is there any 
particular order, or grouping that would help their review.

With so many patches to consider one (the reviewer(s)) gains another 
task of simply trying to prioritise the patches (usually one can take 
big decisions by simply remebering who's series one was interested in).

I expect the clean-ups and 'trivials's' can be managed separately from 
the 'improvements', which would again be separate from the "satging" and 
"Ruby" philosophical discussions.

>   they are going nowhere.
I wouldn't expect 100% success. Every now and again one hears of the 
"here's some patches I've had in my tree for a while" that probably had 
the same early frustrations - they just feel worse the more you produce.

>
> Here is the summary, and you can also find a web version:
> https://github.com/felipec/git/wiki/My-patches
>
> Cheers.
>

Thanks for the summary.
 Philip

> === branch: improve verbose option ===
> Felipe Contreras (2):
> === Reject non-ff pulls by default (v4) ===
> Felipe Contreras (7):
> === remote-helpers: test reorganization (v2) ===
> Felipe Contreras (5):
> === build: add default aliases (v3) ===
> Felipe Contreras (1):
> === Add core.mode configuration (v3) ===
> Felipe Contreras (1):
> === Officially start moving to the term 'staging area' ===
> Felipe Contreras (14):
> === transport-helper: updates (v3) ===
> Felipe Contreras (10):
> === Introduce publish tracking branch ===
> Felipe Contreras (8):
> === New git-related helper (v10) ===
> Felipe Contreras (15):
> === fetch: add new fetch.default configuration ===
> Felipe Contreras (1):
> === Version fixes and cleanups (v4) ===
> Felipe Contreras (2):
> === Trivial paches ===
> Felipe Contreras (20):
> === Massive improvents to rebase and cherry-pick (v6) ===
> Felipe Contreras (28):
> === Support for Ruby (v2) ===
> Felipe Contreras (44):
> === revision: add --except option (v3) ===
> Felipe Contreras (1):
> === sha1-name: refactor get_sha1() parsing ===
> Felipe Contreras (1):
>      sha1-name: refactor get_sha1() parsing
> -- 
> Felipe Contreras
> --

  reply	other threads:[~2013-10-12 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-12  7:24 My patches Felipe Contreras
2013-10-12 16:18 ` Philip Oakley [this message]
2013-10-12 22:33   ` Felipe Contreras
2013-10-14 17:42 ` Junio C Hamano
2013-10-14 21:40   ` Felipe Contreras
2013-10-17 19:54     ` Junio C Hamano
2013-10-17 21:44       ` Felipe Contreras
2013-10-18 11:21         ` Max Horn
2013-10-18 11:41           ` Felipe Contreras
2013-10-18 15:30             ` Theodore Ts'o
2013-10-18 15:49               ` Felipe Contreras
2013-10-18 16:59               ` Junio C Hamano

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=5247B8D59AAE41F3A0D8BF165D2C2BAE@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.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).