Re: Bash git repository on savannah
On 11/28/11 8:34 AM, Chet Ramey wrote: On 11/28/11 4:48 AM, Roman Rakus wrote: On 11/28/2011 06:28 AM, Mike Frysinger wrote: I don't think I'll push every change to git as soon as it happens, but I'm thinking about fairly frequent commits to a `bash-devel' sort of tree. The question is whether or not enough people would be interested in that to make the frequency worth it. i would;) -mike me too OK, that's three. :-) I'd also appreciate each change pushed to the devel git branch. Having 20 years of history in the coreutils git repo has been invaluable for ongoing development. thanks, Pádraig.
Re: Bash git repository on savannah
On 12/7/11 1:52 PM, Chet Ramey wrote: There is now a `devel' branch on the git tree, starting with bash-2.05b and bash-3.0-alpha. There are regular (mostly weekly) snapshot updates, each a separate commit to that branch. The git `devel' branch on savannah now has weekly snapshots up to the end of 2011. This is pretty close to an up-to-date look at the current state of the bash development tree. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: Bash git repository on savannah
On 11/23/11 11:23 PM, Chet Ramey wrote: I spent a little while messing around with git over the past couple of days, and ended up updating the bash git repository on savannah (http://git.savannah.gnu.org/cgit/bash.git to browse the sources). Bash-4.2 patch 20 is the head of the tree, and there's a branch containing the `direxpand' patches that I've posted here. Each bash-4.2 patch is in there as a separate commit. There is now a `devel' branch on the git tree, starting with bash-2.05b and bash-3.0-alpha. There are regular (mostly weekly) snapshot updates, each a separate commit to that branch. I'm currently up to bash-4.0, which represents about five years of work starting in January 2004, and I'm updating as frequently as I have the chance. Each intermediate release (e.g., bash-3.2-beta) for which I have a copy is a separate commit; the milestone releases I don't have are marked with tags to the appropriate weekly snapshot commit. Take a look if you're interested and let me know what you think. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: Bash git repository on savannah
Chet Ramey wrote: I'm thinking about fairly frequent commits to a `bash-devel' sort of tree. The question is whether or not enough people would be interested in that to make the frequency worth it. Anyone wanting to propose a patch would like to prepare it against the most recent state of the tree. And afterwards they are curious to see whether and how the patch made it into the repo. Benno -- http://www.fastmail.fm - The professional email service
Re: Bash git repository on savannah
On 11/28/2011 06:28 AM, Mike Frysinger wrote: I don't think I'll push every change to git as soon as it happens, but I'm thinking about fairly frequent commits to a `bash-devel' sort of tree. The question is whether or not enough people would be interested in that to make the frequency worth it. i would;) -mike me too RR
Re: Bash git repository on savannah
Hello everybody. Just my 2 cents about this ... On Monday 28 November 2011, Chet Ramey wrote: On 11/28/11 4:48 AM, Roman Rakus wrote: On 11/28/2011 06:28 AM, Mike Frysinger wrote: I don't think I'll push every change to git as soon as it happens, but I'm thinking about fairly frequent commits to a `bash-devel' sort of tree. The question is whether or not enough people would be interested in that to make the frequency worth it. i would;) -mike me too OK, that's three. :-) I can't say I'd be really interested, but I surely would be curious, and would greatly appreciate the possibility of peeking into the bash developement process. Apart from that, having a proper, faithful and easily avaiable VCS history would surely help future (so far only hypotetical) maintainers or co-maintainers of Bash. I can say this from experience, since my work as (relatively recent) automake co-maintainer has been and continues to be greatly helped and by the well preserved and fairly complete history in its source repository (history that, BTW, has been successfully preserved in the transition from CVS to git). Regards, Stefano
Re: Bash git repository on savannah
On 11/26/11 2:56 AM, Mike Frysinger wrote: Thanks. I have bash sources going back a number of years, and I can get them into git. It will just take me a while. The question is what to do with that tree once it's assembled. push it to the git repo on svannah you cited above ? Probably. I just have to figure out how to get git to do what I want. do you plan on continuing development on the internal tree, or would you be switching to git fulltime ? I don't think I'll push every change to git as soon as it happens, but I'm thinking about fairly frequent commits to a `bash-devel' sort of tree. The question is whether or not enough people would be interested in that to make the frequency worth it. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: Bash git repository on savannah
On Sunday 27 November 2011 21:31:16 Chet Ramey wrote: On 11/26/11 2:56 AM, Mike Frysinger wrote: Thanks. I have bash sources going back a number of years, and I can get them into git. It will just take me a while. The question is what to do with that tree once it's assembled. push it to the git repo on svannah you cited above ? Probably. I just have to figure out how to get git to do what I want. if you have questions, feel free to post and i'll try to follow up. i know learning curve can be high at first. do you plan on continuing development on the internal tree, or would you be switching to git fulltime ? I don't think I'll push every change to git as soon as it happens, but I'm thinking about fairly frequent commits to a `bash-devel' sort of tree. The question is whether or not enough people would be interested in that to make the frequency worth it. i would ;) -mike signature.asc Description: This is a digitally signed message part.
Re: Bash git repository on savannah
On 11/25/11 2:17 AM, Joachim Schmitz wrote: Does that also mean than these patches are no longer available from ftp://ftp.cwru.edu/pub/bash/bash-4.2-patches/? The newer ones are not, although they are on ftp://ftp.gnu.org/gnu/bash/bash-4.2-patches/. They're there now, it just took me a little while go get them in place. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: Bash git repository on savannah
On 11/24/11 12:36 PM, Mike Frysinger wrote: On Wednesday 23 November 2011 23:23:43 Chet Ramey wrote: I spent a little while messing around with git over the past couple of days, and ended up updating the bash git repository on savannah (http://git.savannah.gnu.org/cgit/bash.git to browse the sources). Bash-4.2 patch 20 is the head of the tree, and there's a branch containing the `direxpand' patches that I've posted here. Each bash-4.2 patch is in there as a separate commit. i thought you were maintaining a private CVS somewhere ? if so, would it be possible to create a git tree from that ? if you want someone else to take care of the details, i can help ... i've converted a bunch of projects in the past over to git from CVS/SVN. Thanks. I have bash sources going back a number of years, and I can get them into git. It will just take me a while. The question is what to do with that tree once it's assembled. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: Bash git repository on savannah
On Friday 25 November 2011 22:28:49 Chet Ramey wrote: On 11/24/11 12:36 PM, Mike Frysinger wrote: On Wednesday 23 November 2011 23:23:43 Chet Ramey wrote: I spent a little while messing around with git over the past couple of days, and ended up updating the bash git repository on savannah (http://git.savannah.gnu.org/cgit/bash.git to browse the sources). Bash-4.2 patch 20 is the head of the tree, and there's a branch containing the `direxpand' patches that I've posted here. Each bash-4.2 patch is in there as a separate commit. i thought you were maintaining a private CVS somewhere ? if so, would it be possible to create a git tree from that ? if you want someone else to take care of the details, i can help ... i've converted a bunch of projects in the past over to git from CVS/SVN. Thanks. I have bash sources going back a number of years, and I can get them into git. It will just take me a while. The question is what to do with that tree once it's assembled. push it to the git repo on svannah you cited above ? do you plan on continuing development on the internal tree, or would you be switching to git fulltime ? -mike signature.asc Description: This is a digitally signed message part.
Re: Bash git repository on savannah
On Wednesday 23 November 2011 23:23:43 Chet Ramey wrote: I spent a little while messing around with git over the past couple of days, and ended up updating the bash git repository on savannah (http://git.savannah.gnu.org/cgit/bash.git to browse the sources). Bash-4.2 patch 20 is the head of the tree, and there's a branch containing the `direxpand' patches that I've posted here. Each bash-4.2 patch is in there as a separate commit. i thought you were maintaining a private CVS somewhere ? if so, would it be possible to create a git tree from that ? if you want someone else to take care of the details, i can help ... i've converted a bunch of projects in the past over to git from CVS/SVN. -mike signature.asc Description: This is a digitally signed message part.
Re: Bash git repository on savannah
Chet Ramey wrote: I spent a little while messing around with git over the past couple of days, and ended up updating the bash git repository on savannah (http://git.savannah.gnu.org/cgit/bash.git to browse the sources). Bash-4.2 patch 20 is the head of the tree, and there's a branch containing the `direxpand' patches that I've posted here. Each bash-4.2 patch is in there as a separate commit. All the released sources back to bash-1.14.7 are there, building on the work Jari Aalto started a couple of years ago. Chet Does that also mean than these patches are no longer available from ftp://ftp.cwru.edu/pub/bash/bash-4.2-patches/? The newer ones are not, although they are on ftp://ftp.gnu.org/gnu/bash/bash-4.2-patches/. Bye, Jojo
Bash git repository on savannah
I spent a little while messing around with git over the past couple of days, and ended up updating the bash git repository on savannah (http://git.savannah.gnu.org/cgit/bash.git to browse the sources). Bash-4.2 patch 20 is the head of the tree, and there's a branch containing the `direxpand' patches that I've posted here. Each bash-4.2 patch is in there as a separate commit. All the released sources back to bash-1.14.7 are there, building on the work Jari Aalto started a couple of years ago. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
