I agree - it probably is possible to write it myself. Obviously, I was hoping
to add to the number of votes that might motivate this work to be done in the
core product rather than as an add-on.
If I had the support of the core team that such an enhancement could eventually
be merged back into the base tree, I might be motivated to work on it (e.g. if
it benefits just me, I'm not sure if its worth the time, but if it benefits many
people, I might be more interested in spending the time) -- is there support for
this?
Do you know anyone who might have already started working on such an plugin?
- Tim
________________________________
From: Jelmer Vernooij <email address hidden>
To: <email address hidden>
Sent: Mon, January 31, 2011 2:03:36 PM
Subject: Re: [Bug 245170] Re: want to store file's modification time during
commit
On Mon, Jan 31, 2011 at 03:52:12PM -0000, Tim Halvorsen wrote:
> Any progress on this? I would very much like to adopt BZR, but will not
> until there is an OPTION to preserve "mtime" as metadata in the
> repository, along with the file content. I have too many tools in my
> tool chain that are dependent on a file's timestamp, including my brain.
This will require a format change, it's not on the current agenda as far as I
know.
It should be possible to work around it by writing a simple plugin that operates
in a fashion similar to e.g. etckeeper. Etckeeper hooks into Bazaar and keeps
a metadata file (".etckeeper") up to date with extra file metadata.
Title:
want to store file's modification time during commit
Status in Bazaar Version Control System:
Confirmed
Bug description:
Checkout should have an option to preserve the modification times of
the files. At least in a lightweight checkout on Windows and NTFS
shared over SMB, the checked out files get the time of the checkout as
their modification time. I'm trying to use bzr to synchronize and
backup files between my laptop and a file server. Other people can
sometimes modify the files on the server while I'm working on the
files on my laptop. I'm keeping the history on my laptop to save disk
space on the server so I use a lightweight checkout. Having the
original (and more meaningful) modification times on the server would
be nice.
I agree - it probably is possible to write it myself. Obviously, I was hoping
to add to the number of votes that might motivate this work to be done in the
core product rather than as an add-on.
If I had the support of the core team that such an enhancement could eventually
be merged back into the base tree, I might be motivated to work on it (e.g. if
it benefits just me, I'm not sure if its worth the time, but if it benefits many
people, I might be more interested in spending the time) -- is there support for
this?
Do you know anyone who might have already started working on such an plugin?
- Tim
_______ _______ _______ _______ ____
From: Jelmer Vernooij <email address hidden>
To: <email address hidden>
Sent: Mon, January 31, 2011 2:03:36 PM
Subject: Re: [Bug 245170] Re: want to store file's modification time during
commit
On Mon, Jan 31, 2011 at 03:52:12PM -0000, Tim Halvorsen wrote:
> Any progress on this? I would very much like to adopt BZR, but will not
> until there is an OPTION to preserve "mtime" as metadata in the
> repository, along with the file content. I have too many tools in my
> tool chain that are dependent on a file's timestamp, including my brain.
This will require a format change, it's not on the current agenda as far as I
know.
It should be possible to work around it by writing a simple plugin that operates
in a fashion similar to e.g. etckeeper. Etckeeper hooks into Bazaar and keeps
a metadata file (".etckeeper") up to date with extra file metadata.
Cheers,
Jelmer
-- /bugs.launchpad .net/bugs/ 245170
You received this bug notification because you are a direct subscriber
of the bug.
https:/
Title:
want to store file's modification time during commit
Status in Bazaar Version Control System:
Confirmed
Bug description:
Checkout should have an option to preserve the modification times of
the files. At least in a lightweight checkout on Windows and NTFS
shared over SMB, the checked out files get the time of the checkout as
their modification time. I'm trying to use bzr to synchronize and
backup files between my laptop and a file server. Other people can
sometimes modify the files on the server while I'm working on the
files on my laptop. I'm keeping the history on my laptop to save disk
space on the server so I use a lightweight checkout. Having the
original (and more meaningful) modification times on the server would
be nice.
To unsubscribe from this bug, go to: /bugs.launchpad .net/bzr/ +bug/245170/ +subscribe
https:/