public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yura Pakhuchiy <y.pakhuchi@sam-solutions.net>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [Linux-NTFS-Dev] [2.6-GIT] NTFS: Release 2.1.25.
Date: Tue, 01 Nov 2005 16:48:08 +0200	[thread overview]
Message-ID: <1130856488.12766.14.camel@pc299.sam-solutions.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0510312136500.10190@hermes-1.csi.cam.ac.uk>

On Mon, 2005-10-31 at 21:54 +0000, Anton Altaparmakov wrote:
> > About me, I did not tested this code before, at least because you had
> > not posted patches to mailing list when you send it to -mm. Sorry, but I
> > do not have git repository.
> 
> That is a lame excuse:
> 
> 1) -mm contains the patch (obviously) as a single file in the split out 
> directory in Andrew's file space on kernel.org (where you would go to 
> download the -mm kernel anyway).
> 
> 2) If you had told me so I could have either posted the patches or put 
> them somewhere for you...  It takes me about 10 seconds to generate them:
> 
> cd /usr/src/ntfs-2.6-devel
> git format-patch -n <linus' head>
> 
> And I get all the patches output to disk...

That was explanation, not excuse. If you want people to test your code,
you should prepare it in form comfortable for them to test. Sorry, but I
do not have time for searching where I can download code you need to
test. I think that many others potential testers do not use git too, and
link to patch or inlined patches much more comfortable for them.

-- 
Best regards,
        Yura


  reply	other threads:[~2005-11-01 14:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 14:22 [2.6-GIT] NTFS: Release 2.1.25 Anton Altaparmakov
2005-10-31 14:24 ` [PATCH 1/17] NTFS: Change ntfs_map_runlist_nolock() to also take an optional attribute search context Anton Altaparmakov
2005-10-31 14:25 ` [PATCH 2/17] NTFS: Change ntfs_attr_find_vcn_nolock() " Anton Altaparmakov
2005-10-31 14:26 ` [PATCH 3/17] NTFS: - Change {__,}ntfs_cluster_free() " Anton Altaparmakov
2005-10-31 14:27 ` [PATCH 4/17] NTFS: - Change ntfs_cluster_alloc() to take an extra boolean parameter Anton Altaparmakov
2005-10-31 14:27 ` [PATCH 5/17] NTFS: Change ntfs_attr_make_non_resident to take the attribute value size Anton Altaparmakov
2005-10-31 14:29 ` [PATCH 6/17] NTFS: Fix ntfs_attr_make_non_resident() to update the vfs inode i_blocks Anton Altaparmakov
2005-10-31 14:30 ` [PATCH 7/17] NTFS: Add fs/ntfs/attrib.[hc]::ntfs_attr_extend_allocation() Anton Altaparmakov
2005-10-31 14:31 ` [PATCH 8/17] NTFS: Implement fs/ntfs/inode.[hc]::ntfs_truncate() Anton Altaparmakov
2005-10-31 14:32 ` [PATCH 9/17] NTFS: Enable ATTR_SIZE attribute changes in ntfs_setattr() Anton Altaparmakov
2005-10-31 14:32 ` [PATCH 10/17] NTFS: In attrib.c::ntfs_attr_set() call balance_dirty_pages_ratelimited() Anton Altaparmakov
2005-10-31 14:33 ` [PATCH 11/17] NTFS: Remove address space operations ->prepare_write and ->commit_write Anton Altaparmakov
2005-10-31 14:36 ` [PATCH 12/17] NTFS: The big ntfs write(2) rewrite has arrived Anton Altaparmakov
2005-10-31 14:38 ` [PATCH 13/17] NTFS: $EA attributes can be both resident non-resident Anton Altaparmakov
2005-10-31 14:38 ` [PATCH 14/17] NTFS: Fix serious data corruption issue when writing Anton Altaparmakov
2005-10-31 14:40 ` [PATCH 15/17] NTFS: Use %z for size_t to fix compilation warnings. (Andrew Morton) Anton Altaparmakov
2005-10-31 14:41 ` [PATCH 16/17] NTFS: Fix compilation warnings with gcc-4.0.2 on SUSE 10.0 Anton Altaparmakov
2005-10-31 14:42 ` [PATCH 17/17] NTFS: Document extended attribute ($EA) NEED_EA flag Anton Altaparmakov
2005-10-31 19:30 ` [Linux-NTFS-Dev] [2.6-GIT] NTFS: Release 2.1.25 Yuval
2005-10-31 20:05   ` Anton Altaparmakov
2005-10-31 20:24 ` Yura Pakhuchiy
2005-10-31 20:49   ` Anton Altaparmakov
2005-10-31 21:25     ` Yura Pakhuchiy
2005-10-31 21:54       ` Anton Altaparmakov
2005-11-01 14:48         ` Yura Pakhuchiy [this message]
2005-11-01 14:56           ` Anton Altaparmakov
2005-11-01 15:01             ` Yura Pakhuchiy
2005-11-01 16:22               ` Anton Altaparmakov

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=1130856488.12766.14.camel@pc299.sam-solutions.net \
    --to=y.pakhuchi@sam-solutions.net \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=pakhuchiy@gmail.com \
    --cc=torvalds@osdl.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