Re: Tools, options or workflow for checking modifications in outdated CVS checkout
W dniu 22.08.2022 o 15:27, Mikolaj Kucharski pisze: I forgot to add, currently I'm using: cvs -q diff | grep -ve '^[ +-=@Rrd]' however I'm wondering is there anything better? On Mon, Aug 22, 2022 at 12:32:24PM +, Mikolaj Kucharski wrote: Hi, I have random OpenBSD CVS checkouts across different directories and machines. I work on something, life interrupts, I come back to it after longer period of time. In the meantime CVS repo moves forward and my checkout is out of date. How I can efficiently check for M's (modified) in the repo, without actually updating the repo? I'm looking for something a long the lines, if a file is outdated, but NOT modified, no output is produced. However if the file is locally modified, then path should be printed to stdout. Do you guys know is there any tool available like that? It's important for me that during that process, repo stays read-only and no modifications are taking place to the checkout. To simulate outut I'm looking for something like this: $ cvs -q up -PAd ? sbin/ifconfig/ifconfig.c-combined ? sbin/ifconfig/obj ? sys/arch/amd64/compile/GENERIC.MP/obj ? usr.sbin/sysupgrade/sysupgrade.diff ? usr.sbin/sysupgrade/sysupgrade.patch M sbin/ifconfig/ifconfig.8 M sbin/ifconfig/ifconfig.c M sys/net/if_wg.c M sys/net/if_wg.h However above output does update, so modifies the repo, which I wouldn't want to happen. Please CC me in any replies. Maybe copying repo to another directory (with hardlinks so it doesn't take as much space), then updating that copy, getting list of updated files, then check each file if it's modified locally in original repo? This could be a good starting point, even if it's not ideal solution. I belive rsync had option to use hardlinks instead of copying. -- Łukasz Moskała
Re: Tools, options or workflow for checking modifications in outdated CVS checkout
On 2022-08-22, Mikolaj Kucharski wrote: > Hi, > > I have random OpenBSD CVS checkouts across different directories and > machines. I work on something, life interrupts, I come back to it > after longer period of time. In the meantime CVS repo moves forward and > my checkout is out of date. > > How I can efficiently check for M's (modified) in the repo, without > actually updating the repo? > > I'm looking for something a long the lines, if a file is outdated, but > NOT modified, no output is produced. However if the file is locally > modified, then path should be printed to stdout. > > Do you guys know is there any tool available like that? > > It's important for me that during that process, repo stays read-only and > no modifications are taking place to the checkout. > > To simulate outut I'm looking for something like this: > > $ cvs -q up -PAd > ? sbin/ifconfig/ifconfig.c-combined > ? sbin/ifconfig/obj > ? sys/arch/amd64/compile/GENERIC.MP/obj > ? usr.sbin/sysupgrade/sysupgrade.diff > ? usr.sbin/sysupgrade/sysupgrade.patch > M sbin/ifconfig/ifconfig.8 > M sbin/ifconfig/ifconfig.c > M sys/net/if_wg.c > M sys/net/if_wg.h > > However above output does update, so modifies the repo, which I wouldn't > want to happen. "cvs -n up" ? there's also "cvsu" from cvsutils, but it doesn't correctly parse CVS/Entries files in some cases relating to add/rm. still, that's probably what I use most often for this, it's pretty fast. > Please CC me in any replies. > Mikolaj > > -- Please keep replies on the mailing list.
Re: Tools, options or workflow for checking modifications in outdated CVS checkout
On 2022/08/22 12:32:24 +, Mikolaj Kucharski wrote: > Hi, > > I have random OpenBSD CVS checkouts across different directories and > machines. I work on something, life interrupts, I come back to it > after longer period of time. In the meantime CVS repo moves forward and > my checkout is out of date. > > How I can efficiently check for M's (modified) in the repo, without > actually updating the repo? > > I'm looking for something a long the lines, if a file is outdated, but > NOT modified, no output is produced. However if the file is locally > modified, then path should be printed to stdout. > > Do you guys know is there any tool available like that? > > It's important for me that during that process, repo stays read-only and > no modifications are taking place to the checkout. > > To simulate outut I'm looking for something like this: > > $ cvs -q up -PAd > ? sbin/ifconfig/ifconfig.c-combined > ? sbin/ifconfig/obj > ? sys/arch/amd64/compile/GENERIC.MP/obj > ? usr.sbin/sysupgrade/sysupgrade.diff > ? usr.sbin/sysupgrade/sysupgrade.patch > M sbin/ifconfig/ifconfig.8 > M sbin/ifconfig/ifconfig.c > M sys/net/if_wg.c > M sys/net/if_wg.h > > However above output does update, so modifies the repo, which I wouldn't > want to happen. > > Please CC me in any replies. I think -n is what you're looking for: % cvs -n up -d cvs update: Updating . M xcompmgr.c ? obj cvs update: Updating man
Tools, options or workflow for checking modifications in outdated CVS checkout
Hi, I have random OpenBSD CVS checkouts across different directories and machines. I work on something, life interrupts, I come back to it after longer period of time. In the meantime CVS repo moves forward and my checkout is out of date. How I can efficiently check for M's (modified) in the repo, without actually updating the repo? I'm looking for something a long the lines, if a file is outdated, but NOT modified, no output is produced. However if the file is locally modified, then path should be printed to stdout. Do you guys know is there any tool available like that? It's important for me that during that process, repo stays read-only and no modifications are taking place to the checkout. To simulate outut I'm looking for something like this: $ cvs -q up -PAd ? sbin/ifconfig/ifconfig.c-combined ? sbin/ifconfig/obj ? sys/arch/amd64/compile/GENERIC.MP/obj ? usr.sbin/sysupgrade/sysupgrade.diff ? usr.sbin/sysupgrade/sysupgrade.patch M sbin/ifconfig/ifconfig.8 M sbin/ifconfig/ifconfig.c M sys/net/if_wg.c M sys/net/if_wg.h However above output does update, so modifies the repo, which I wouldn't want to happen. Please CC me in any replies. -- Regards, Mikolaj
Re: Tools, options or workflow for checking modifications in outdated CVS checkout
I forgot to add, currently I'm using: cvs -q diff | grep -ve '^[ +-=@Rrd]' however I'm wondering is there anything better? On Mon, Aug 22, 2022 at 12:32:24PM +, Mikolaj Kucharski wrote: > Hi, > > I have random OpenBSD CVS checkouts across different directories and > machines. I work on something, life interrupts, I come back to it > after longer period of time. In the meantime CVS repo moves forward and > my checkout is out of date. > > How I can efficiently check for M's (modified) in the repo, without > actually updating the repo? > > I'm looking for something a long the lines, if a file is outdated, but > NOT modified, no output is produced. However if the file is locally > modified, then path should be printed to stdout. > > Do you guys know is there any tool available like that? > > It's important for me that during that process, repo stays read-only and > no modifications are taking place to the checkout. > > To simulate outut I'm looking for something like this: > > $ cvs -q up -PAd > ? sbin/ifconfig/ifconfig.c-combined > ? sbin/ifconfig/obj > ? sys/arch/amd64/compile/GENERIC.MP/obj > ? usr.sbin/sysupgrade/sysupgrade.diff > ? usr.sbin/sysupgrade/sysupgrade.patch > M sbin/ifconfig/ifconfig.8 > M sbin/ifconfig/ifconfig.c > M sys/net/if_wg.c > M sys/net/if_wg.h > > However above output does update, so modifies the repo, which I wouldn't > want to happen. > > Please CC me in any replies. > -- Regards, Mikolaj
