git.git: topics and things like that

git.git: topics and things like that

[Xavier Maillard]

Hi,

This may appear as a stupid question but as I can not find
anything about this, I am just asking.

So, how is git development organised ? I saw there are topics but
I do not know how patches are applied mainline (onto tip of
master).

Would you mind explaining this very quickly so I can understand
messages "What's new in git.git" ? :)

Thank you very much and sorry to bother with this basic question.

Xavier

Re: git.git: topics and things like that

[Shawn O. Pearce]

Xavier Maillard <zedek@gnu.org> wrote:
> This may appear as a stupid question but as I can not find
> anything about this, I am just asking.
> 
> So, how is git development organised ? I saw there are topics but
> I do not know how patches are applied mainline (onto tip of
> master).

Junio covered this well in the past.  The text has been copied into
the wiki:

  http://git.or.cz/gitwiki/Notes

But I have to admit, it took me a while to find it.  ;-)
 
-- 
Shawn.

Re: git.git: topics and things like that

[Xavier Maillard]

   Junio covered this well in the past.  The text has been copied into
   the wiki:

     http://git.or.cz/gitwiki/Notes

   But I have to admit, it took me a while to find it.  ;-)

Thank you very much. I will copy/paste it locally.

Xavier

Re: git.git: topics and things like that

[Junio C Hamano]

Xavier Maillard <zedek@gnu.org> writes:

> So, how is git development organised ? I saw there are topics but
> I do not know how patches are applied mainline (onto tip of
> master).

Your maintainer posts "A note from the maintainer" to the list
every once in a while describing this exact issue.

The last such message was on Feb 16th

	Message-ID: <7vire120qc.fsf@assigned-by-dhcp.cox.net>

gmane has it as article 39954:

	http://article.gmane.org/gmane.comp.version-control.git/39954

Re: git.git: topics and things like that

[Xavier Maillard]

Hi,

   > So, how is git development organised ? I saw there are topics but
   > I do not know how patches are applied mainline (onto tip of
   > master).

   Your maintainer posts "A note from the maintainer" to the list
   every once in a while describing this exact issue.

I never have seen such message but I will read it now.

Anyway, thank you.

Xavier

Re: git.git: topics and things like that

[Junio C Hamano]

Xavier Maillard <zedek@gnu.org> writes:

>    Your maintainer posts "A note from the maintainer" to the list
>    every once in a while describing this exact issue.
>
> I never have seen such message but I will read it now.

Heh, how new are you to the list?

Is every three months not often enough?  Meaning, is expecting
new users to look back that much backlog in the list archive too
much to ask?

Re: git.git: topics and things like that

[Steven Grimm]

Junio C Hamano wrote:
> Heh, how new are you to the list?
>
> Is every three months not often enough?  Meaning, is expecting
> new users to look back that much backlog in the list archive too
> much to ask?
>   

I went looking for an answer to the "what does 'pu' mean?" question when 
I first joined the list, failed to find one, then stumbled across it by 
accident while randomly skimming the archives. "A message from the 
maintainer" is not at first glance an obvious subject line to click on 
if you're searching for that kind of introductory information -- putting 
on my "unfamiliar with the list's conventions" hat, I'd expect a message 
of that title to contain something like, "Hey guys, can you help test 
XYZ?" or "The list archives will be moving in two weeks" or, more 
likely, "Our hosting is costing us too much and we need donations."

It would be convenient for new users and, I assume, not much additional 
effort to put the URL of that Wiki page at the top of the "what's 
cooking" messages. Barring that, maybe the "A message from the 
maintainer" email should be titled "Introduction to git project 
management" or something similar that would make it immediately obvious 
to a new user that it's something they should read to get general 
background information about the project.

Just IMO. At this point I've been lurking here long enough that I don't 
need it for myself, but I do remember wishing that info were easier to find.

-Steve

Re: git.git: topics and things like that

[Junio C Hamano]

Steven Grimm <koreth@midwinter.com> writes:

> ... maybe the "A message from the
> maintainer" email should be titled "Introduction to git project
> management" or something similar that would make it immediately
> obvious to a new user that it's something they should read to get
> general background information about the project.

I do not necessarily think that is a better title.  It not just
talks the project management, but a note from the maintainer in
general.  In the future it might talk about even more things.

Moderated newsgroups tend to have "foo.bar.baz FAQ" periodical
postings, but I'd rather not make me the authoritative FAQ
maintainer, as git is about distributed development and
borrowing the convention from heavily-centralized moderated
world feels wrong.  Besides, it is something that does not have
to be done by me.

I just expected people to pay attention to what the maintainer
has to say (in addition to what the well known list regulars
have to say), if they wanted to know what the project is about,
and "A note from the maintainer" (the message _always_ had that
title) would be a good enough title for finding that.

Any volunteers to maintain FAQ for the list?

Re: git.git: topics and things like that

[Martin Langhoff]

On 3/26/07, Junio C Hamano <junkio@cox.net> wrote:
> Heh, how new are you to the list?
>
> Is every three months not often enough?  Meaning, is expecting
> new users to look back that much backlog in the list archive too
> much to ask?

I'd say he probably didn't know. Maybe an extra paragraph at the end
of the  README  ? along the lines of ...

The project maintainer sends out regular emails to the list titled "A
note from the maintainer", "What's cooking in git.git" and "Unresolved
issues". These messages and the discussion following them are a good
reference for project status, development direction and bugfixing
tasks.


cheers,


martin

Re: git.git: topics and things like that

[Junio C Hamano]

"Martin Langhoff" <martin.langhoff@gmail.com> writes:

> I'd say he probably didn't know. Maybe an extra paragraph at the end
> of the  README  ? along the lines of ...
>
> The project maintainer sends out regular emails to the list titled "A
> note from the maintainer", "What's cooking in git.git" and "Unresolved
> issues". These messages and the discussion following them are a good
> reference for project status, development direction and bugfixing
> tasks.

Thanks; that is a wonderful, constructive suggestion.  Would
have been even better if it was presented in a patch form ;-).

Re: git.git: topics and things like that

[Jakub Narebski]

Martin Langhoff wrote:

> On 3/26/07, Junio C Hamano <junkio@cox.net> wrote:
>> Heh, how new are you to the list?
>>
>> Is every three months not often enough?  Meaning, is expecting
>> new users to look back that much backlog in the list archive too
>> much to ask?
> 
> I'd say he probably didn't know. Maybe an extra paragraph at the end
> of the  README  ? along the lines of ...
> 
> The project maintainer sends out regular emails to the list titled "A
> note from the maintainer", "What's cooking in git.git" and "Unresolved
> issues". These messages and the discussion following them are a good
> reference for project status, development direction and bugfixing
> tasks.

Add "What's in git.git (stable)" to that.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git