Jeff King <peff@xxxxxxxx> writes:
>> In a sense, this is what I do as well. As you mentioned, I push to "ko"
>> to publish, but when I "fetch" (or "pull") from "origin", I get the public
>> copy I have at kernel.org like everybody else, and I do fetch every time
>> after I push to "ko" to get the updated preformatted HTML and man page
>> branches.
>
> Interesting. Is your fetch from "ko" a no-op, or are you using it to
> syncrhonize development between different machines?
Preformatted html and man pages are made when I push the integrated source
branches out, triggered from the post-update hook at kernel.org. I do not
format them on my box.
I say "git push ko", take a sip of tea, and after k.org finishes the
asciidoc dance "git fetch ko" to get them all, before pushing
remotes/ko/{maint,master,next,pu,todo,html,man} to secondary sites.
> I think it is important to note that calling them both "origin" is
> definitely the wrong thing. The proposal is instead that "git push"
> without a remote would default to something besides "origin". For people
> who publish multiple places, it might even make sense for it to be an
> iterative push to each place.
Either we add branch.<name>.pushremote or push.defaultremote then?
--
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