Vitor, I know it has been a long time, but I finally tried the below, and it works for me. I was doing things wrong at first, but I think I finally understand what is going on... First, the branchList is great, that is what I needed. Now I can completely ignore the p4 branches. It would be great if there was an option to not have it query p4 branches at all, because we have so many branches here it takes forever, and I am just using branchList. What I did for now was to use your branchUser option, and pass it a bogus username, like "XXXXXX". At least this way it returns fast, but would be nice to not have it try to query at all. I think I understand now why all this is needed if you want it to detect branches on its own. Since in Perforce branches are just directories, there is no way to tell if a directory is a branch or not, and people could organize branches in an arbitrary directory structure. I was thinking you could look at sibling directories under the same parent, which may be common, but there is no way to know for sure, so better to be explicit. The other odd issue is that if you do not add the new branch to branchList (or p4 branches if you are using them) before you do the git-p4 sync, then since it goes through change numbers in order, it will never go back again and catch the branch in a change it already synced. This is why I could never get it to work, because I never had it in place before I synced the relevant change. What I realized though is that I can always do a "git-p4 sync --detect-branches //depot/foo/bar/@all" again, even though I already have the most recent change, and it will re-detect any branches I missed (given I have since added them to branchList). What I had been thinking though is that if it had already detected branches once, it could at least update the remote p4 branches it already knew about to point at the latest revision, just not try to detect new ones, and not rely on branchList. Of course you would still need branchList to detect any new branches. Anyway, works a lot better than it did before. Thanks, Mike On Fri, May 13, 2011 at 10:31 AM, Vitor Antunes <vitor.hda@xxxxxxxxx> wrote: > Hi Michael, > > Michael Horowitz <michael.horowitz <at> ieee.org> writes: > >> >> Vitor, >> >> > Could you please search for the following set of patches in this >> > mailing list? >> > >> > [PATCH v2 0/3] git-p4: Improve branch support >> > >> > I think I sent v2 twice somehow, so please make sure you pick the >> > latest ;) >> > In these patches I add the possibility to use a "git-p4.branchList" >> > configuration to define the branches. The patch is still to be >> > approved because most people in the mailing list do not use branch >> > detection, but I use it daily and it is working in my side. Could >> > you please test it? >> >> Can you send this patch again? It looks like you had previously >> responded to the list only, so I never got this message, as I wasn't >> on the list at the time (I am now). I only saw this because I was >> searching the archive for something else. I searched for the patch, >> but the actual patch body doesn't seem to be in the archive. > > I am also not in the mailing list, I just follow its RSS and try to > follow up on the git-p4 related topics ;) That is the reason why you > were not included in the reply. > > But I have been a bit busy and did not see this email passing by. Sorry. > Luckily I had a tab opened in this thread, which I looked at today > wondering what it was about! :P > > Please follow the link to the thread [1] and you can open each of the > entries. Take care not to apply patch 1/3 as it may require you to clone > everything again. > >> Thanks, >> >> Mike >> > > Regards, > Vitor > > [1] http://thread.gmane.org/gmane.comp.version-control.git/167998/focus=168000 > > > -- > 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 -- 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