On Thu, Jul 17, 2014 at 12:35 PM, Stephan Beal
wrote:
>
> On Thu, Jul 17, 2014 at 6:23 PM, Ron W wrote:
>
>> The fossil export command has the options --export-marks and
>> --import-marks for storing and reading RIDs of exported data in a named
>> file. The first time you create an export to a s
On Thu, Jul 17, 2014 at 6:23 PM, Ron W wrote:
> The fossil export command has the options --export-marks and
> --import-marks for storing and reading RIDs of exported data in a named
> file. The first time you create an export to a specific, intended receiving
> repo, you use just --export-marks.
On Thu, Jul 17, 2014 at 2:35 AM, Gour wrote:
> Ron W writes:
>
> > Reading more about bundles, they appear, in Fossil terms, to be what
> would
> > be sent out by a push, or similar to an incremental export (yes, Fossil
> > supports incremental exports).
>
> Hmm, can you tell me more about incre
Ron W writes:
> Reading more about bundles, they appear, in Fossil terms, to be what would
> be sent out by a push, or similar to an incremental export (yes, Fossil
> supports incremental exports).
Hmm, can you tell me more about incremental exports?
Iirc, using incremental import from Git was
On Wed, Jul 16, 2014 at 2:03 AM, Gour wrote:
> Ron W writes:
>
> > As best I can determine from a description of "hg bundle", a patch file
> > provides similar functionality.
>
> I believe it's more...darcs has it, same with bzr & hg...it is the
> ability to create 'bundle' which contains approp
Ron W writes:
> As best I can determine from a description of "hg bundle", a patch file
> provides similar functionality.
I believe it's more...darcs has it, same with bzr & hg...it is the
ability to create 'bundle' which contains appropriate context of the
patch so that it's easy to send it e.g
6 matches
Mail list logo
