On Wed, Jan 11, 2012 at 2:35 AM, Richard Hartmann
wrote:
> Hi all,
>
> while bup works as a special remote, it's not a proper repo in and as of
> itself.
>
> With proper tracking in the git-annex or a different branch, it should
> be possible to make (some) git-annex repos persistent and change
>
On Wed, Jan 11, 2012 at 12:39, Adam Spiers wrote:
> Is your point that a bup remote is persistent (i.e. not lossy) but
> does not track history
It does track history, but not in a format that is immediately accessible.
> whereas a normal annex is the opposite - lossy
> (when an annexed file's
On mer., janv. 11, 2012 at 12:56:49 +0100, Richard Hartmann wrote:
>
> Old data can be useful. Point in case, I may change GPS coordinates in
> EXIF data and correct timestamps based on that info. Maybe I will even
> correct white balance, etc. Still, I would want to keep full history
> forever in
On Wed, Jan 11, 2012 at 20:44, Vincent Demeester wrote:
> That also sound useful for me, and somehow with a similar use case (my
> photography folder).
I just realized that a special git remote may make more sense than a
special bup remote.
This is, after all, _exactly_ what we would need, in t
On 11 Jan 2012 at 20:06Z, Richard Hartmann wrote:
> I just realized that a special git remote may make more sense than a
> special bup remote.
> This is, after all, _exactly_ what we would need, in this case.
> If git-annex detects that it's being run in a "real" git repo, it
> could, hopefully,
