On Dec 19, 2007 3:23 AM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > On Wed, 19 Dec 2007, Dana How wrote: > > I'd like to move some stuff currently in a p4 repository into git. > > The directory structure within the repo is 13 levels deep; > > I didn't design it nor can I change it. > > > > ... The > > basic commit:file syntax doesn't accept relative paths. I am not > > specifically hung up on the commit:./path syntax; I just want some > > notation that will get those 13 directories from $cwd instead of > > making me type them again. > > I think new feature like this should be postponed after 1.5.4 is out; > we are now in feature freeze (only bugfixes are accepted). OK. This is all the conversation that resulted from Alex's RFC. > That said, does git-showrel solution proposed by Johannes Schindelin > in > Message-ID: <Pine.LNX.4.64.0712182250040.23902@xxxxxxxxxx> > http://permalink.gmane.org/gmane.comp.version-control.git/68840 > work for you? > > Below version of git-showrel script which uses proposed 'commit:./relpath' > syntax (it could be improved, of course): > > cat > git-showrel <<\EOF > #!/bin/sh > > rel=$(git rev-parse --show-prefix 2>/dev/null) > git show $(echo "$@" | sed -e "s!:./!:${rel}!") > > EOF It's definitely true I could use this for now. In the long run (meaning after the feature freeze) I don't view this as adequate for 2 reasons: (1) I would like a consistent interpretation of commit:path wherever it is accepted; and (2) If a novice types bad arguments to git-showrel , they are probably going to be very confused by its error messages which are a response to a munged version of their command line. Thanks, -- Dana L. How danahow@xxxxxxxxx +1 650 804 5991 cell - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
