Am 15.08.2012 19:30, schrieb Junio C Hamano:
The current rule is very
simple and understandable.  You either say from the command line
exactly what should happen (refspec without colon is the same as the
refspec with colon at the end, meaning "do not track"; if you want
to track, you write what to update with the fetch), or we use the
configured refspec (which again spells what should happen).

Couldn't a similar new rule just say that refspec <name> is a short for <name>:<name> ?

The exception would be in the case of a URL as remote, but that would not be surprising to anyone, as there is no obvious target for the update

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to