From: Ivan Shapovalov <intelfx@intelfx.name>
To: Edward Shishkin <edward.shishkin@gmail.com>,
ReiserFS development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 Upstream Git Repositories on GitHub
Date: Fri, 30 Sep 2016 09:56:24 +0300 [thread overview]
Message-ID: <1475218584.19471.3.camel@intelfx.name> (raw)
In-Reply-To: <b2b6b412-6a80-37d3-0055-3fe84a195afd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6109 bytes --]
On 2016-09-28 at 12:17 +0200, Edward Shishkin wrote:
> On 09/27/2016 11:51 PM, Ivan Shapovalov wrote:
> > On 2016-09-27 at 23:47 +0200, Edward Shishkin wrote:
> > > On 09/27/2016 08:36 PM, Ivan Shapovalov wrote:
> > > > On 2016-09-27 at 16:13 +0200, Edward Shishkin wrote:
> > > > > On 09/27/2016 04:43 AM, Ivan Shapovalov wrote:
> > > > > > On 2016-09-27 at 00:37 +0200, Edward Shishkin wrote:
> > > > > > > On 09/27/2016 12:05 AM, Ivan Shapovalov wrote:
> > > > > > > > On 2016-09-24 at 22:16 +0200, Edward Shishkin wrote:
> > > > > > > > > Hello everyone,
> > > > > > > > >
> > > > > > > > > I have set up the updated Namesys repositories at my
> > > > > > > > > Github
> > > > > > > > > page.
> > > > > > > > > Those repositories are supposed to contain the latest
> > > > > > > > > updates
> > > > > > > > > in
> > > > > > > > > the (stable) master branch and in other
> > > > > > > > > (experimental)
> > > > > > > > > branches
> > > > > > > > > that
> > > > > > > > > I'll announce.
> > > > > > > > >
> > > > > > > > > 1) https://github.com/edward6/reiser4
> > > > > > > > >
> > > > > > > > > This is a "standalone" reiser4 tree, which doesn't
> > > > > > > > > include
> > > > > > > > > specific
> > > > > > > > > changes of Linux kernel needed for reiser4 port. Such
> > > > > > > > > changes
> > > > > > > > > can
> > > > > > > > > be
> > > > > > > > > found at the project's page on Sourceforge:
> > > > > > > > > https://sourceforge.net/projects/reiser4/
> > > > > > > > >
> > > > > > > > > An example of work with the standalone reiser4 tree:
> > > > > > > > >
> > > > > > > > > . Patch the respective kernel with the latest
> > > > > > > > > available
> > > > > > > > > stuff
> > > > > > > > > from
> > > > > > > > > Sourceforge;
> > > > > > > > > . cd to the "fs" directory;
> > > > > > > > > . delete the directory reiser4;
> > > > > > > > > . instead of the deleted stuff clone the standalone
> > > > > > > > > reiser4
> > > > > > > > > repository from Github;
> > > > > > > > > . build and install as usual.
> > > > > > > > >
> > > > > > > > > 2) Libaal and Reiser4progs:
> > > > > > > > >
> > > > > > > > > https://github.com/edward6/libaal
> > > > > > > > > https://github.com/edward6/reiser4progs
> > > > > > > > >
> > > > > > > > > Before building Libaal and Reiser4progs execute the
> > > > > > > > > ./prepare
> > > > > > > > > script,
> > > > > > > > > which will create files needed for build process.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Edward.
> > > > > > > >
> > > > > > > > Wow, finally.
> > > > > > > >
> > > > > > > > Maybe we could avoid that "all changes for 10 years"
> > > > > > > > commit?
> > > > > > >
> > > > > > > Hi Ivan,
> > > > > > > Sorry, don't have a time to granulate it.
> > > > > > >
> > > > > > > > I tried to keep track of all patches since 3.2...
> > > > > > >
> > > > > > > There will be "all changes for 6 years" commit.
> > > > > > > Is it much better?
> > > > > >
> > > > > > So well, I finished splitting off all known diffs from that
> > > > > > big
> > > > > > commit.
> > > > > > Tt was 12k(+)/8k(-), now it is 7k(+)/7k(-).
> > > > > >
> > > > > > The updated branch is here: https://github.com/intelfx/reis
> > > > > > er4
> > > > > > (unfortunately, not fast-forward).
> > > > > >
> > > > > > Moreover, my tree has accumulated quite a few differences
> > > > > > from
> > > > > > your
> > > > > > one. I've dropped trivial discrepancies (comments,
> > > > > > formatting
> > > > > > etc.)
> > > > > > and put the larger ones in separate branches:
> > > > > >
> > > > > > 1. https://github.com/intelfx/reiser4/tree/differences/enot
> > > > > > ty
> > > > > > (unsupported ioctls return -ENOTTY, not -ENOSYS)
> > > > > >
> > > > > > 2. https://github.com/intelfx/reiser4/tree/differences/migr
> > > > > > atep
> > > > > > age
> > > > > > (the ->migratepage() implementation, which I still do
> > > > > > not
> > > > > > completely
> > > > > > understand, but it works)
> > > > > >
> > > > > > 3. https://github.com/intelfx/reiser4/tree/differences/rena
> > > > > > meat
> > > > > > 2
> > > > > > (renameat2(RENAME_NOREPLACE) implementation, which
> > > > > > you
> > > > > > haven't
> > > > > > merged somewhy)
> > > > > >
> > > > > > 4. https://github.com/intelfx/reiser4/tree/differences/adju
> > > > > > st-t
> > > > > > o-3.
> > > > > > 15
> > > > > > (part of porting to 3.15 which, again, you haven't
> > > > > > merged
> > > > > > somewhy)
> > > > > >
> > > > > > These branches are on top of that granular "master".
> > > > > > Anyway, please take a look.
> > > > >
> > > > > It was definitely useful work,
> > > > > I'll look at those differences..
> > > >
> > > > Maybe you could also consider rebasing things on top of that
> > > > extracted
> > > > granular history?
> > > >
> > >
> > > Interesting idea, but I am not able to estimate
> > > complexity of such rebasing for now.
> > >
> >
> > While we do not have any forks and can afford non-fast-forward
> > updates
> > of master, the complexity is almost nil.
> >
> > To rebase your format41 branch, one can do this:
> >
> > git rebase --preserve-merges --onto
> > 3c7b3c5802e20381496f641fe64b6c1573228c6e
> > 8a896fd48ed35c7dfa0188f9b7f4cbdfd469cacb format41
> >
> > where 8a896fd is merge-base of format41 and master (that big
> > commit),
> > and 3c7b3c5 is the corresponding commit of the synthesized history.
> >
> > Both commits have identical file content (`git diff 8a896fd
> > 3c7b3c5`
> > yields empty output).
>
> OK, everything went smoothly,
> Thanks for scrupulously archiving things!
>
> Edward.
In meantime, I have also generated a history of the kernel side changes
(again, starting with 3.2). They are pretty small.
Do I understand correctly that the kernel folks are reluctant to merge
these ~150 lines?
--
Ivan Shapovalov / intelfx /
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-30 6:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:16 Reiser4 Upstream Git Repositories on GitHub Edward Shishkin
2016-09-25 0:36 ` Christian Kujau
2016-09-26 22:05 ` Ivan Shapovalov
2016-09-26 22:37 ` Edward Shishkin
2016-09-26 23:03 ` Ivan Shapovalov
2016-09-27 1:43 ` Ivan Shapovalov
2016-09-27 14:04 ` Edward Shishkin
2016-09-27 2:43 ` Ivan Shapovalov
2016-09-27 14:13 ` Edward Shishkin
2016-09-27 18:36 ` Ivan Shapovalov
2016-09-27 21:47 ` Edward Shishkin
2016-09-27 21:51 ` Ivan Shapovalov
2016-09-28 10:17 ` Edward Shishkin
2016-09-28 10:36 ` Ivan Shapovalov
2016-09-28 13:56 ` Edward Shishkin
2016-09-28 14:44 ` Edward Shishkin
2016-09-28 15:03 ` Ivan Shapovalov
2016-09-28 19:58 ` Edward Shishkin
2016-09-28 21:50 ` Ivan Shapovalov
2016-09-29 15:07 ` Edward Shishkin
2016-09-30 3:28 ` Ivan Shapovalov
2016-10-04 15:52 ` Edward Shishkin
2016-09-30 6:56 ` Ivan Shapovalov [this message]
2016-10-03 14:33 ` Edward Shishkin
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=1475218584.19471.3.camel@intelfx.name \
--to=intelfx@intelfx.name \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.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).