Re: Bash source repository
On Mon, Nov 2, 2009 at 10:40 PM, Bob Proulx wrote: > Chet Ramey wrote: >> Jari Aalto was setting up a git repository of current and older bash >> versions on savannah. I'll keep him up to date with public versions >> of bash (including, probably, public betas). > > It looks like it has just recently been partially implemented. > > http://git.savannah.gnu.org/cgit/bash.git > > But only at the major release points. No patches have been applied. > But the available history seems to all be there. I can't see the history there, actually. Could not locate the individual commits and its associated changelogs, only big commit blobs containing whole releases. Mind explaining? Thank you, André
sudo: command: not found
run the command "drcomd" ,successful! but run command "sudo drcomd" ,return "sudo : drcomd: command not found" under both (fedora)the PATH is /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin it's really confusing!!!
Colorizing PS4... needing PS4_AFTER ?
Hello, I wish I could use PS4 to colorize debugging lines, like: PS4='\033[37m+ ' But I need to reset the color at the end of the line. I wish there were a similar variable to be able to reset the ansi code at the end of the line, like PS4_AFTER='\033[0m+' Do you know a hack to reset color at the end of each debug line ? FYI, my current hack is: # in bashrc: export PS4='+\302\240' alias shdebugpipe='sed -e "s/^+\o302\o240.*/\x1b[37m\0\x1b[0m/"' # then invoke script with: bash -x ./foo.sh 2>&1 | shdebugpipe (I replaced the regular space with a non-breakable space[1] in PS4 to avoid highlighting script output. The one I am using is little bit more complex. it uses BOM[2] instead of NBSP): # in bashrc: export PS4='\357\273\277#$LINENO:' alias shdebugpipe='sed -e "s/^\o357\o273\o277.*/\x1b[37m\0\x1b[0m/"' Franklin (Please CC me, I am not subscribed to this list). [1] NBSP: http://en.wikipedia.org/wiki/Non-breaking_space [2] BOM: http://en.wikipedia.org/wiki/Byte_order_mark
Re: Bash source repository
André Goddard Rosa wrote: > On Mon, Nov 2, 2009 at 10:40 PM, Bob Proulx wrote: >> Chet Ramey wrote: >>> Jari Aalto was setting up a git repository of current and older bash >>> versions on savannah. I'll keep him up to date with public versions >>> of bash (including, probably, public betas). >> It looks like it has just recently been partially implemented. >> >> http://git.savannah.gnu.org/cgit/bash.git >> >> But only at the major release points. No patches have been applied. >> But the available history seems to all be there. > > I can't see the history there, actually. > > Could not locate the individual commits and its associated changelogs, > only big commit blobs containing whole releases. > > Mind explaining? That's how I prefer it. I don't do public development on savannah, and I do controlled test releases. 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 source repository
Chet Ramey schrieb: > That's how I prefer it. I don't do public development on savannah, and > I do controlled test releases. The official patches should be there as individual commits. Though, I admit it's not a small amount of work to do all that for the past releases. Such a GIT or SVN repository technically is easy to do, but who feeds it :( J.
Re: Bash source repository
Jan Schampera wrote: > The official patches should be there as individual commits. Though, I > admit it's not a small amount of work to do all that for the past > releases. Such a GIT or SVN repository technically is easy to do, but > who feeds it :( Moving forward from now it should be reasonably easy to keep it up to date with official patches. But recreating the history of all of the past releases and all official patches for all past releases would be significant effort. Just trying to locate all of them would be quite the task. If someone actually had all of the releases and all of the patches together (the hard part) then I would be willing to put them together (the easy part) for the version control history. But as you say, then someone still needs to feed it when new official patches are released. Bob
