On 16:21 Fri 12 Nov 2010, Michal Marek wrote:
On Thu, Nov 11, 2010 at 03:49:19PM -0800, Brandon Philips wrote:
+commit=$(patch-tag -p git-commit $FILE | grep -i "git-commit:" | sed "s%.*:\s\(.*\)%\1%g")
patch-tag is not in PATH.
Right, I will do one of these: $(dirname "$0"
+if [ "z$mainline" = "z" ]; then + git show $commit > /dev/null + if git show $commit > /dev/null 2> /dev/null; then + merged=$(basename $DIR) + patch-tag -A Patch-mainline="Merged into $merged" $FILE + exit 0
What's the intended use of this? I assume you have a separate checkout for each subsystem tree, but concluding anything from the directory name is too error-prone IMO.
Yes, this is my exact use case.
E.g. all patches from me would have "Merged into linux-2.6", people might rename their checkouts etc. If you want to guess some reliable name, you would probably have to find out what refs/remotes/$repository/$branch has the commit and then run 'git config remote.$repository.url' to get a name that makes sense in the Patch-mainline header. Or something among these lines.
Good point, I will add a command line argument to let the user specify what they would like the Merged into tag to say. Thanks for the review. Cheers, Brandon -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org