From: Petr Baudis Date: Mon, 19 Sep 2005 16:34:39 GMT Subject: Re: What shall we do with the GECOS field again? Message-ID: <20050919163439.GB18320@pasky.or.cz> In-Reply-To: <432EE46F.9000806@gmail.com> Dear diary, on Mon, Sep 19, 2005 at 06:16:47PM CEST, I got a letter where A Large Angry SCM told me that... > >Sure, many organizations bake their own, but I'd argue that the majority > >doesn't. > > The point is we should not be telling them what and how to put stuff in > the GECOS field. The point is that our guess should be something which works for the most people. > >>AND/OR to include > >>the what Git thinks the user's name name might be in the commit message > >>template they're editing (like the file list). > > > >I think that's a good idea, as long as people are told how to change it > >(i.e., an envvar -- NOT by editing the file). > > Yes. I'll change cg-commit to always include the name/email fields in its template. I think it's verbose enough as it is now, though, and I don't want it to bloat it with more generic help text. I've expanded the documentation of cg-commit on the GIT_ variables and that ought to be enough. :-) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ If you want the holes in your knowledge showing up try teaching someone. -- Alan Cox