From: anonymous <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue71] Move sources last update from .sup/sources.yaml
Date: Tue, 23 Feb 2010 22:17:36 +0000 [thread overview]
Message-ID: <1266963456.92.0.651747611938.issue71@masanjin.net> (raw)
In-Reply-To: <1266963456.92.0.651747611938.issue71@masanjin.net>
New submission from anonymous:
I save sup configuration files on sources control so I can move freely between
computers. .sup/sources.yaml is updated on every pull - makes it very annoying
to commit all the time.
Can you separate the "where" in sources from the "when"? This way I can track
only the "where" file.
Thanks,
--
Miki
----------
messages: 178
nosy: anonymous
priority: feature request
ruby_version: 1.8.7
status: unread
sup_version: 0.10.1
title: Move sources last update from .sup/sources.yaml
_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue71>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next parent reply other threads:[~2010-02-23 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:17 anonymous [this message]
2010-02-24 0:34 ` Ben Walton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1266963456.92.0.651747611938.issue71@masanjin.net \
--to=sup-bugs@masanjin.net \
--cc=sup-devel@rubyforge.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