Thread (10 messages) flat view 10 messages, 4 authors, 2016-06-15

Re: tags and patches

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:43:16

Hi,

On Thu, 14 Jun 2007, Geoff Russell wrote:
On 6/14/07, Johannes Schindelin [off-list ref] wrote:
quoted
AFAIK patches are not supposed to _contain_ patches.
Is this a typo? I expected patches to contain tags, not other patches.
Actually, two typos. Sorry. "AFAIK" -> "AFAICT", and the rest should 
actually have been written as "formatted patches are not supposed to 
contain tags."
quoted
What you want is probably a bundle. You don't want a collection of 
diffs with comments on them, but you want a collection to reacreate 
the history the other side has.
I didn't know about bundles but do now.  However "git bundle --help" 
tells me "No manual entry for git-bundle" despite git-bundle.html being 
in the Documentation directory.
... which probably means that your man pages, and therefore your Git 
installation, is not up-to-date.
I'm trying to work out if I want to use git to manage a software 
distribution problem. I distribute release v1.0 to people then later I 
want to email them a patch to take them from v1.0 to v1.1.  I can 
probably live without the tags, but am just surprised that patches don't 
send them.
Patches are just files of the format that "diff" outputs, and "patch" 
accepts. There was never any possibility to change anything but files.

But then, usually people put the version _into_ files. So I suspect you 
really don't need tags, if you _have_ to send patches. Because if you 
_have_ to send patches, your recipients probably don't use Git, and could 
not use those tags anyway.

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help