On 3/12/2014 9:59 AM, Junio C Hamano wrote:
Ilya Bobyr <ilya.bo...@gmail.com> writes:
I though that an example just to describe `argh' while useful would
look a bit disproportional, compared to the amount of text on
--parseopt.
But now that I've added a "Usage text" section to looks quite in place.
Good thinking.
I was also wondering about the possible next step(s). If you like
the patch will you just take it from the maillist and it would
appear in the next "What's cooking in git.git"? Or the process is
different?
It goes more like this:
Thank you for all the details.
- A topic that is in a good enough shape to be discussed and moved
forward is given its own topic branch and then merged to 'pu', so
that we do not forget. The topic enters "What's cooking" at this
stage.
I can not find this particular patch in the latest "What's cooking" email.
Is there something I can do?
It does not seems like there is a lot of interest, so I am not sure
there will be a lot of discussion.
It is a minor fix and considering the number of the emails on the list,
I do not unexpected this kind of stuff to be very popular.
But it seems like a valid improvement to me.
Maybe I am missing something?
Same questions about this one:
[PATCH] gitk: replace SHA1 entry field on keyboard paste
http://www.mail-archive.com/git@vger.kernel.org/msg45040.html
I think they are more or less similar, except that the second one is
just trivial.
- Discussion on the topic continues on the list, and the topic can
be replaced or built upon while it is still on 'pu' to polish it
further.
. We may see a grave issue with the change and may discard it
from 'pu'.
. We may see a period of inaction after issues are pointed out
and/or improvements are suggested, which would cause the topic
marked as stalled; this may cause it to be eventually discarded
as "abandoned" if nobody cares deeply enough.
- After a while, when it seems that we, collectively as the Git
development circle, agree that we would eventually want that
change in a released version in some future (not necessarily in
the upcoming release), the topic is merged to 'next', which is
the branch Git developers are expected to run in their daily
lives.
. We may see some updates that builds on the patches merged to
'next' so far to fix late issues discovered.
. We may see a grave issue with the change and may have to
revert & discard it from 'next'.
- After a while, when the topic proves to be solid, it is merged to
'master', in preparation for the upcoming release.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
