unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: Project idea: a poor man's VC backend
Date: Thu, 11 Dec 2014 20:44:54 +0100	[thread overview]
Message-ID: <87egs66keh.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <83388mt6dp.fsf@gnu.org>


On 2014-12-11, at 18:59, Eli Zaretskii wrote:

>> From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
>> Date: Thu, 11 Dec 2014 17:09:05 +0100
>> 
>> In a recent question on ESE
>> (http://emacs.stackexchange.com/questions/2849/save-current-file-with-a-slightly-different-name)
>> the topic of versioning by means of putting a timestamp into the
>> filename came up again (it does have its place, especially when
>> communicating with people unable to learn a real VCS).
>> 
>> Just wondering: would it be possible/easy/reasonable to provide
>> something like this within the Emacs VC framework?
>
> Are you talking about time-stamp.el?

Not really.

I mean that e.g. C-x v v will "do the right thing", for instance:

I'm editing file.el (the only file in the current directory).  I press
C-x v v.  I'm asked for a "commit message" and the current contents of
file.el are save as e.g. file.el.2014-12-11-20:39:01-CET or something
like that, with the "commit message" put at the beginning in a comment
(for example).  I edit it further, and C-x v v behaves similarly.  Then,
I can press C-x v =, and see the diff between the current version and
the last stamped one.  Or C-u C-x v = and be asked (with autocompletion)
for the timestamp.  Then, have similar commands for analogs of
blame/annotate, revert to earlier versions etc.

Of course, it's impossible to recreate the functionality of Git in this
way.  Or even RCS, I'm afraid.  But for many use cases this might be
enough (for instance, one/two authors working on a single LaTeX file of
the paper).  (One paticular functionality that would be difficult to
implement would be branching; while possible, it might be even
misleading and hence dangerous.  Remember, the target would be the
users, uhm, not wise enough to use a real VCS;-).)

The rationale would be that e.g. if I work with a non-computer-savvy
researcher, any "real" VCS might be confusing; I might be expected to
e.g. send him file versions with a timestamp in the filename etc.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  reply	other threads:[~2014-12-11 19:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 16:09 Project idea: a poor man's VC backend Marcin Borkowski
2014-12-11 16:38 ` Stefan Monnier
2014-12-11 19:46   ` Marcin Borkowski
2014-12-11 20:17     ` Stefan Monnier
2014-12-11 20:48       ` Marcin Borkowski
2014-12-11 17:59 ` Eli Zaretskii
2014-12-11 19:44   ` Marcin Borkowski [this message]
2014-12-12  8:11     ` Rainer M Krug
2015-01-14 21:41       ` Marcin Borkowski
2015-01-14 21:58         ` Dmitry Gutov
2015-01-15 13:10         ` Doug Lewan
     [not found]   ` <mailman.15879.1418327119.1147.help-gnu-emacs@gnu.org>
2015-01-15 13:48     ` Damien Wyart
2015-01-15 20:17       ` Joost Kremers
2015-01-15 23:35         ` Marcin Borkowski
2015-01-16 17:17         ` Bob Proulx

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87egs66keh.fsf@wmi.amu.edu.pl \
    --to=mbork@wmi.amu.edu.pl \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).