From: vapo@sgi.com (Vlad Apostolov)
To: sgi.bugs.xfs@engr.sgi.com
Cc: xfs@oss.sgi.com
Subject: PARTIAL TAKE 957103 -
Date: Tue, 16 Jan 2007 17:08:45 +1100 (EST) [thread overview]
Message-ID: <20070116060845.0D2E958F92CD@chook.melbourne.sgi.com> (raw)
Fix update_26_xfs script to avoid problems with new files and deleting mainline-patches
Date: Tue Jan 16 17:08:22 AEDT 2007
Workarea: chook.melbourne.sgi.com:/build/vapo/isms/xfs-cmds
Inspected by: chatz
The following file(s) were checked into:
longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb
Modid: master-melb:xfs-cmds:27936a
xfsmisc/update_26_xfs - 1.4 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsmisc/update_26_xfs.diff?r1=text&tr1=1.4&r2=text&tr2=1.3&f=h
- Exit if lsdiff is not in path, otherwise new files will not be marked fetal. Add mainline-patches to skip list so it is not deleted.
next reply other threads:[~2007-01-16 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 6:08 Vlad Apostolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 6:01 PARTIAL TAKE 957103 - Vlad Apostolov
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=20070116060845.0D2E958F92CD@chook.melbourne.sgi.com \
--to=vapo@sgi.com \
--cc=sgi.bugs.xfs@engr.sgi.com \
--cc=xfs@oss.sgi.com \
/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