From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] cwfs fsmempercent
Date: Mon, 5 May 2014 02:43:24 +0200 [thread overview]
Message-ID: <5e68664a37b65df6c26c6f3748a97173@felloff.net> (raw)
In-Reply-To: <554d640d37a831251f341115852c07a7@felloff.net>
you could also just delete /dist/plan9front/.hg and copy
it back from the iso (or from dump or whatever), then do a
hg pull; then; hg update. hg is very good at not destroying
local changes it doesnt know about.
so even if you have an old .hg/ repository, but new working files,
it will just report them as local modifications. once you
hg pull and hg update, it should see that the files are all
the same as in the repository and the modifications should
be gone. hg status -q to verify.
--
cinap
next prev parent reply other threads:[~2014-05-05 0:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 4:25 9FRONT "опен-сссл" Released sl
2014-04-28 10:52 ` cwfs fsmempercent arisawa
2014-04-28 17:08 ` [9front] " cinap_lenrek
2014-04-28 17:26 ` cinap_lenrek
2014-04-28 22:55 ` arisawa
2014-04-29 20:11 ` cinap_lenrek
2014-04-30 14:41 ` Kenji Arisawa
2014-04-30 20:14 ` cinap_lenrek
2014-05-01 10:39 ` 9pc64 arisawa
2014-05-01 11:07 ` [9front] 9pc64 Aram Hăvărneanu
2014-05-01 14:06 ` arisawa
2014-05-01 14:25 ` cinap_lenrek
2014-05-01 14:39 ` cinap_lenrek
2014-05-01 15:27 ` cinap_lenrek
2014-05-01 21:49 ` Kenji Arisawa
2014-05-01 21:51 ` cinap_lenrek
2014-05-01 23:22 ` Kenji Arisawa
2014-05-01 23:34 ` Kenji Arisawa
2014-05-02 0:22 ` cinap_lenrek
2014-05-02 11:02 ` Aram Hăvărneanu
2014-05-04 5:24 ` malloc Kenji Arisawa
2014-05-04 8:22 ` [9front] malloc arisawa
2014-05-04 12:40 ` [9front] cwfs fsmempercent arisawa
2014-05-04 23:22 ` cinap_lenrek
2014-05-05 0:11 ` arisawa
2014-05-05 0:31 ` cinap_lenrek
2014-05-05 0:43 ` cinap_lenrek [this message]
2014-05-05 2:04 ` arisawa
2014-05-05 4:32 ` cinap_lenrek
2014-05-05 8:00 ` arisawa
2014-05-05 11:15 ` arisawa
2014-05-05 12:08 ` arisawa
2014-05-03 0:37 ` cinap_lenrek
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=5e68664a37b65df6c26c6f3748a97173@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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 NNTP newsgroup(s).