Hi, On Mon, 27 Oct 2008, Marc Branchaud wrote:I agree; I do not think that you need an adjective here. I'd also recommend thinking about the branches as "local" and "remote". Not anything with "tracking" or "trailing" or somesuch. When you really look at it from the non-technical view point, even the branches you have in refs/remotes/*/ are the remote branches; the fact that you have a local cached version of them is just a minor implementation detail. And as to the "--track" thing? I'd not make that big a deal out of it. At most, I'd say that a certain local branch happens to follow a certain remote branch, but that can change over time, right? (Just change branch.<name>.merge...) Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Luciano Rocha | usb hdd problems with 2.6.27.2 |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
