git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [egit PATCH] avoiding output in the error log

From
Shawn O. Pearce <spearce@spearce.org>
Date
Aug 27, 2008, 22:00 UTC
Message-ID
<20080827220022.GP26523@spearce.org>
In-Reply-To
<200808272350.56819.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
Show 10 quoted lines
> > > 
> > > Shawn, you removed the test from the code in 4a230ea1. Perhaps you could care to
> > > comment on this patch to restore the test, though slightly different.
> > > 
> > > 		if (r.isAccessible())
> > > 			r.setSessionProperty(GITFOLDERDIRTYSTATEPROPERTY, null);
> 
> Good. So then the question is whether we should use isAccessible() or exists()? Normally
> this makes no difference, but for a Project (at least) there is a difference. I project that exits
> is not accessible when closed. 

It _has_ to be isAccessible(). You cannot get or set a session property on a closed project.

-- 
Shawn.
Previous: Robin Rosenberg
Message 5 of 5 in “avoiding output in the error log”
  1. avoiding output in the error logrobert_no.spam_m@yahoo.fr, Aug 27, 2008
  2. Robin RosenbergAug 27, 2008
  3. Shawn O. PearceAug 27, 2008
  4. Robin RosenbergAug 27, 2008
  5. Shawn O. PearceAug 27, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.