On Fri, Mar 21, 2008 at 01:39:11PM -0400, Avery Pennarun wrote: > On Fri, Mar 21, 2008 at 5:13 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Paul Gardiner <osronline@xxxxxxxxxx> writes: > > > I need a command that will find the remote branch from which > > > the currently checked out branch was started. I don't know > > > git very well, and the only way I can think to do it so far > > > is to iterate over the remote branches and find the one > > > for which git-rev-list <branch>..HEAD gives the smallest > > > number of objects. I'm guessing there must be a better > > > way. Any ideas? > > > > There will be _no_ way. It is simply impossible. > > > > $ git checkout -b my-new-branch origin/somerandombranch~27^2^2~23 > > > > is a perfectly valid way to create a new branch. > > > > You would probably want to re-think in a bigger picture, _why_ > > you would want to find such information, [...] > > I frequently want to do this. Basically, I start from "some version" > of the upstream program, and I put together some patches, then I want > to use rebase to reorder and recombine them before I send them in. So you're looking to do a git rebase -i? > In order to do this, however, I'm forced to remember where I got my > "original" version from, which isn't even that important. As the > developer of a particular patch, all I *really* should have to know > is: a) here are the things I added since I made my topic branch, and > b) here is the branch I want to rebase them onto so I can submit my > cleaned patches upstream. Why are you forced to remember? If you don't want to transplant the patches onto where the remote branch is now, then you just need to pick a commit on your current branch that is before any commit that you want to reorder/recombine and do a git rebase -i <sha1>. (It should be easy to pick a commit from git log. Perhaps it's the first one with and author that isn't you. Alternatively, if you don't want to look at the log and you know you haven't made more than N commits you could just git rebase -i HEAD~N.) If you want to rebase them on to the latest version of the remote branch then it's even simpler. You just do: git rebase -i remote/branch I'm not sure I understand why you need to know where your original branch was made from? Charles. -- 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
