On 06/15/2012 01:34 AM, Shishir Gowda wrote:
> Hi Emmanuel,
>
> Please change to release-3.3 branch on the git.
> 'git checkout -b release-3.3 origin/release-3.3'
A slight alternative is to create the branch as an explicit tracking branch, so
that "git pull" etc. do the right things without needing to specify the repo
and branch every time.
git branch -t release-3.3 origin/release-3.3
git checkout release-3.3
AFAIK the -b and -t functions are not available in a single command, because
that would be convenient and this is git. ;)
>
> Apply your changes, and commit them.
>
> The rfc.sh script will identify it as release-3.3 and do the needfull.
>
> With regards,
> Shishir
>
> ----- Original Message -----
> From: "Emmanuel Dreyfus" <m...@netbsd.org>
> To: gluster-devel@nongnu.org
> Sent: Friday, June 15, 2012 10:39:33 AM
> Subject: [Gluster-devel] submit changes to release-3.3
>
> Hi
>
> Is there some doc explaining how should I submit changes to release-3.3?
> I mean what should I tell to git and rfc.sh...
>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
