Re: "commit"s without "from" in fast-import

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Eyvind Bernhardsen <eyvind-git@...>
Cc: James Westby <jw+debian@...>, <git@...>, Ian Clatworthy <ian.clatworthy@...>
Date: Tuesday, March 18, 2008 - 10:06 pm

Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> wrote:

Agreed.
 

I'm leaning towards leaving it in the language as allowed, and thus
documenting that this is not only possible, but actively used by
importers as it can be an easy way to setup a subsequent change
with no initial files.

But I have to wonder what the bzr-fast-import folks would say.
I've CC'd in James and Ian, as they have been working on the bzr
side for a little.

James, Ian -- to give you the short backstory we are talking about
creating a new branch _without_ a "from", but instead using a single
"merge" to specify the sole ancestor revision of a new commit to
be placed on the new branch.  This allows the frontend to supply
all files for the tree as none were inherited from the sole ancestor.

The other (more obvious?) approach to accomplish the same result
is to use "from" followed by a "filedeleteall" to clear the files,
then supply the new files.  Both approaches have the exact same
result in git-fast-import.

-- 
Shawn.
--
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
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: "commit"s without "from" in fast-import, Shawn O. Pearce, (Tue Mar 18, 10:06 pm)
Re: "commit"s without "from" in fast-import, James Westby, (Wed Mar 19, 2:39 pm)