Re: [hwloc-devel] commit messages

[Brice Goglin]

Done at https://git.open-mpi.org/trac/hwloc/wiki/CommitMessages
I also updated some references to SVN in other wiki pages.
Brice


Le 28/09/2013 14:19, Jeff Squyres (jsquyres) a écrit :
> This sounds good.  Can you add this to the trac wiki?  
>
> (e.g., MPICH did something like this when they converted to git)
>
>
> On Sep 28, 2013, at 8:15 AM, Brice Goglin  wrote:
>
>> Let's discuss some rules for commit messages. I used svn propedit often
>> in the past, that's not possible anymore once pushed to the main git repo.
>>
>> 1) Obviously we should follow the commit log convention:
>>
>> one short line description (less than 80 chars)
>> 
>> full description
>>
>>
>> 2) When backporting patches between public branches, use git cherry-pick
>> *-x* so that the old commit ID is recorded is the new commit log. If
>> you're working in your private branches, this may not be needed (if the
>> old commit ID may change before you actually push it).
>>
>> 3) Configure your username and email properly before commtting.
>>
>> git config user.email 
>> git config user.name "First Last"
>>
>> This goes into .git/config. Add --global to make these global for all
>> your git repos (goes into ~/.gitconfig)
>>
>> What else?
>>
>> Brice
>>
>> ___
>> hwloc-devel mailing list
>> hwloc-de...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
>

Re: [hwloc-devel] commit messages

[Jeff Squyres (jsquyres)]

I pinged IU.  We ran into this problem during the svn->git transition, but I 
thought DongInn fixed it.  Sorry...


On Sep 28, 2013, at 8:23 AM, Brice Goglin  wrote:

> I can't login on Trac. Requested a new password, doesn't work either.
> 
> Brice
> 
> 
> Le 28/09/2013 14:19, Jeff Squyres (jsquyres) a écrit :
>> This sounds good.  Can you add this to the trac wiki?  
>> 
>> (e.g., MPICH did something like this when they converted to git)
>> 
>> 
>> On Sep 28, 2013, at 8:15 AM, Brice Goglin  wrote:
>> 
>>> Let's discuss some rules for commit messages. I used svn propedit often
>>> in the past, that's not possible anymore once pushed to the main git repo.
>>> 
>>> 1) Obviously we should follow the commit log convention:
>>> 
>>> one short line description (less than 80 chars)
>>> 
>>> full description
>>> 
>>> 
>>> 2) When backporting patches between public branches, use git cherry-pick
>>> *-x* so that the old commit ID is recorded is the new commit log. If
>>> you're working in your private branches, this may not be needed (if the
>>> old commit ID may change before you actually push it).
>>> 
>>> 3) Configure your username and email properly before commtting.
>>> 
>>> git config user.email 
>>> git config user.name "First Last"
>>> 
>>> This goes into .git/config. Add --global to make these global for all
>>> your git repos (goes into ~/.gitconfig)
>>> 
>>> What else?
>>> 
>>> Brice
>>> 
>>> ___
>>> hwloc-devel mailing list
>>> hwloc-de...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
>> 
> 
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [hwloc-devel] commit messages

[Brice Goglin]

I can't login on Trac. Requested a new password, doesn't work either.

Brice


Le 28/09/2013 14:19, Jeff Squyres (jsquyres) a écrit :
> This sounds good.  Can you add this to the trac wiki?  
>
> (e.g., MPICH did something like this when they converted to git)
>
>
> On Sep 28, 2013, at 8:15 AM, Brice Goglin  wrote:
>
>> Let's discuss some rules for commit messages. I used svn propedit often
>> in the past, that's not possible anymore once pushed to the main git repo.
>>
>> 1) Obviously we should follow the commit log convention:
>>
>> one short line description (less than 80 chars)
>> 
>> full description
>>
>>
>> 2) When backporting patches between public branches, use git cherry-pick
>> *-x* so that the old commit ID is recorded is the new commit log. If
>> you're working in your private branches, this may not be needed (if the
>> old commit ID may change before you actually push it).
>>
>> 3) Configure your username and email properly before commtting.
>>
>> git config user.email 
>> git config user.name "First Last"
>>
>> This goes into .git/config. Add --global to make these global for all
>> your git repos (goes into ~/.gitconfig)
>>
>> What else?
>>
>> Brice
>>
>> ___
>> hwloc-devel mailing list
>> hwloc-de...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
>

Re: [hwloc-devel] commit messages

[Jeff Squyres (jsquyres)]

This sounds good.  Can you add this to the trac wiki?  

(e.g., MPICH did something like this when they converted to git)


On Sep 28, 2013, at 8:15 AM, Brice Goglin  wrote:

> Let's discuss some rules for commit messages. I used svn propedit often
> in the past, that's not possible anymore once pushed to the main git repo.
> 
> 1) Obviously we should follow the commit log convention:
> 
> one short line description (less than 80 chars)
> 
> full description
> 
> 
> 2) When backporting patches between public branches, use git cherry-pick
> *-x* so that the old commit ID is recorded is the new commit log. If
> you're working in your private branches, this may not be needed (if the
> old commit ID may change before you actually push it).
> 
> 3) Configure your username and email properly before commtting.
> 
> git config user.email 
> git config user.name "First Last"
> 
> This goes into .git/config. Add --global to make these global for all
> your git repos (goes into ~/.gitconfig)
> 
> What else?
> 
> Brice
> 
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

[hwloc-devel] commit messages

[Brice Goglin]

Let's discuss some rules for commit messages. I used svn propedit often
in the past, that's not possible anymore once pushed to the main git repo.

1) Obviously we should follow the commit log convention:

one short line description (less than 80 chars)

full description


2) When backporting patches between public branches, use git cherry-pick
*-x* so that the old commit ID is recorded is the new commit log. If
you're working in your private branches, this may not be needed (if the
old commit ID may change before you actually push it).

3) Configure your username and email properly before commtting.

git config user.email 
git config user.name "First Last"

This goes into .git/config. Add --global to make these global for all
your git repos (goes into ~/.gitconfig)

What else?

Brice