René Scharfe [off-list ref] writes:
I don't know if it's a good idea, but perhaps we don't even need a new
option. We could change how pathspecs of untracked files are handled:
Instead of aborting we could include them in the archive. (Sounds like
the simplest possible interface, but may have practical problems.)
One practical problem is that users who do this
$ git archive HEAD Documentation/ | tar tf -
would be expecting (at least) two different things, depending on the
situation they are in.
So at least you'd need an "--include-untracked" option, I guess.
Am 04.01.2018 um 19:22 schrieb Junio C Hamano:
René Scharfe [off-list ref] writes:
quoted
I don't know if it's a good idea, but perhaps we don't even need a new
option. We could change how pathspecs of untracked files are handled:
Instead of aborting we could include them in the archive. (Sounds like
the simplest possible interface, but may have practical problems.)
One practical problem is that users who do this
$ git archive HEAD Documentation/ | tar tf -
would be expecting (at least) two different things, depending on the
situation they are in.
So at least you'd need an "--include-untracked" option, I guess.
Right, this breaks down with directories -- most build artifacts (e.g.
.o files) are probably not meant to end up in archives. We could still
do it for regular files and symlinks. Perhaps that's too confusing,
though, and an --add-untracked-file parameter (or whatever we want to
call it) is the way to go.
René